Fix k8s_drain runs into timeout with pods from stateful sets. #793
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Fixes #792 .
The function
wait_for_pod_deletion
in k8s_drain never checks on which node a pod is actually running:This means that if a pod is successfully evicted and restarted with the same name on a new node,
k8s_drain
does not notice and thinks that the original pod is still running. This is the case for pods which are part of a stateful set.ISSUE TYPE
COMPONENT NAME
k8s_drain